2.5.128 Core Enhancements

In This Topic...

Managing Custom Client Data (CustomClient Workflow Container)

A new CustomClient workflow container has been introduced. In addition to holding the content maintained through the OWClient Standard Workflow Container, the CustomClient container allows the user to create fields, panels, grids, and screens to capture and display custom client data.

Custom client fields, panels, grids, and screens can be configured within the CustomClient container and then added to the policy submission workflow to allow users to reference additional client information during the submission process. Once values are saved in these custom fields, they are mapped to all future workflow submissions where the same Individual or Company client is selected.

The following field control types are supported for custom client data in the CustomClient workflow container.

  • Checkbox
  • Checkbox Group
  • Combo Box
  • Date Picker
  • Drop Down
  • Include/Exclude
  • Multi-Select
  • Radio Button
  • Rich Text
  • Text Area
  • Textbox
  • Textbox (Decimal)
  • Textbox (Email)
  • Textbox (Integer)

This excludes the File Upload field control type.

There are three instances where client data is retrieved from the Client record and used in the policy.

  • When selecting a client on a New Business transaction.
  • When changing the client on a New Business transaction.
  • When creating a new Policy Transaction.

    Note that when creating a Policy Transaction, the system always pulls client information from the Client record, (ignoring the Field Mapping Rules - Copy settings, and therefore never copying from the source transaction).

Notes:

The system does not block the user from creating an unsupported field Control Type in the CustomClient workflow container. However, doing so will cause unexpected behaviors or errors to occur.

After making changes to the CustomClient workflow container, Policy workflows that are receiving content from the shared CustomClient container must also be re-published to propagate the changes to the submission workflow.

Only a single custom Client workflow is supported by the system. It is recommended to use the provided CustomClient workflow container, and not create another custom workflow container with Client as the Functional Area.

Ability to Assign Policies as Claims-made or Occurrence-based

Previously, the Bridge Specialty Suite only supported Occurrence-based policies. In this case, the policy covers claims caused by an event that occurs during the policy term. Coverage is dependent on the timing of the event.

The concept of Claims-made policies has now been introduced to the system and covers claims that are submitted during the policy period. In this case, coverage is dependent on the timing of the claim itself, and not the event that caused the claim. The incident must occur between the policy start date (effective date) and the end of the policy (valid until date), before the ERP begins.

A new setting called Product Type has been added to the Master Cover - General Information page. Users are required to select whether the policies associated to the master cover are Claims-made or Occurrence-based. By default, all new and existing Master Covers are set to Occurrence-based.

New Master Cover Settings for ERP Endorsements on Claims-made Policies

Claims-made insurance policies are now supported in the Bridge Specialty Suite, as previously, the system only supported Occurrence-based policies. As a result of this new feature, Master Covers that are configured as Claims-made can offer Extended Reporting Period (ERPEndorsements.

A new field called Product Type has been added to the Master Cover - General Information page. When creating a new master cover, users can select whether the policies created under this master cover will be Claims-made or Occurrence-based. Note that when the Claims-made option is selected, certain quote calculations are no longer applied to Premium Types on ERP Endorsements.

Upon Calculate Quote on an ERP transaction, there are several changes that can occur. The operation is similar to New Business or Renewal transactions with the following differences:

  • Premium is not prorated.
  • Quote Options for Policy Term Type set to ERP Endorsement are evaluated, while the others (New Business & Renewal) are skipped.
  • The following validations are skipped:

    • Referral
    • Compliance
    • Manual Bind
  • Given that the above validations are skipped, the policy transaction’s status can be either:

    • Quoted
    • Incomplete (if there’s a Data or Quote Validation)
  • Automatic emails from the Get Quote / Recalculate Quote – ERP Endorsement workflow event type are sent.

Note that when Claims-made is selected as the Product Type, the Allow Program Policies setting in the Master Cover is not available for ERP transactions.

Note: By default, all existing Master Covers are set to Occurrence-based and users should not change this setting. If necessary, contact your Insurity Account Representative to request a data maintenance.

A new panel, Claims-made Settings, has been added to the Master Cover - Policy Settings page. This panel is only displayed when Claims-made is selected in the Product Type field on the General Information page, and includes the Allow ERP Endorsement checkbox. The Allow ERP Endorsement checkbox enables policies created under this master cover to offer ERP Endorsements.

When the Allow ERP Endorsement checkbox is selected, the ERP Endorsement Duration List and ERP Endorsement Default fields are displayed. Users must create an Option List with the duration options in the Option List Management section. A default value (in years) must also be provided for the ERP Endorsement Default field on the Master Cover - Policy Settings page.

The Quote Options grid on the Master Cover - Quote Options page now displays a column for the Policy Term Type, in which either New Business or Renewal, or ERP Endorsement is displayed. Note that all existing Quote Options are set to New Business or Renewal by default. When configuring new Quote Options, the Policy Term Type field is available for users to select which Policy Term Type is applicable. Quote Options for ERPs must be fully configured including rates, taxes and fees, deductibles, limits, and insuring conditions.

When Allow ERP Endorsement is selected, the Extended Reporting Period Quote Validity setting is displayed on the Master Cover - Automatic Processing page. This setting is used to specify the eligibility period of a tail coverage quote. If there is no activity on an ERP transaction for a period of time, or if there are other reasons to feel the business has been lost, the quote can be marked as Lost.

Finally, three new Workflow Events have been added for Master Cover - E-mail Configurations, the Bind - ERP Endorsement, Get Quote / Recalculate Quote - ERP Endorsement, and Mark As Lost - ERP Endorsement events. These events will trigger the appropriate e-mails to be sent, based on the configuration, upon binding an ERP Endorsement, quoting or recalculating a quoted ERP Endorsement, or when marking the ERP as Lost (manually or automatically). All existing Workflow Events have been updated to include ERP Endorsements.

  • For details on the Product Type setting on the Master Cover page, see the General Information section.
  • For details on the Allow ERP Endorsement setting on the Policy Settings page, see the Policy Settings section.
  • For details on ERP Endorsement Quote Options on the Master Cover - Quote Options page, see the Quote Options section.
  • For details on the Extended Reporting Period Quote Validity setting on the Master Cover - Automatic Processing page, see the Automatic Processing section.
  • For details on the new Workflow Events on the Master Cover - E-mail Configurations page, see the E-mail Configurations section.
  • For details on the creating the ERP Endorsement Duration List option list, see the Managing Options Lists section.

ERP Endorsement Transactions Processing

With the implementation of Claims-made policies and the new Master Cover settings for ERP Endorsements, the Bridge Specialty Suite has introduced new functionality that allows users to create and manage ERP Endorsement policy terms and transactions.

Note that the BindPolicy and CreatePolicy security rights have been enhanced to include creating and binding ERP Endorsements. Users must have these rights in order to perform the actions described below.

When this feature is enabled, users can:

  • Create an ERP Endorsement - Transaction is in Incomplete status.
  • Quote an ERP Endorsement - Transaction is in Quoted status.
  • Bind an ERP Endorsement - Transaction is in Bound status.
  • Void an ERP Endorsement - Transaction is in Bound status, the Correction Type is Void, and an Offset transaction is created.
  • Mark an ERP Endorsement as Lost - Transaction is in Lost status.
  • Delete an ERP Endorsement - Transaction is deleted.

Upon creating an ERP Endorsement, a new term is initiated with the ERP Endorsement transaction.

The following changes have been implemented to account for ERP Endorsement transactions:

In the Workflow Container management page for Fields, the Field Mapping Rules panel now includes ERP Endorsements. Additionally, the Copy Row On panel in the Grids management page and Field Evaluation Rule configurations are also supported for ERP Endorsements.

A new action link, ERP Endorsement, has been added to the Actions widget. An ERP Endorsement can only be created from either the earliest cancelled policy term, or if no term is cancelled, from the latest Bound term. All future terms must be Declined or Voided. The source transaction the ERP is created from must be in Bound status in the source term (cancelled or bound) and all other transactions in the term must be in an end-of-life status.

If an ERP Endorsement is created for a policy that has the Master Cover setting for Automatic Renewal checked, an error message will display. For any policy that has an ERP transaction, the policy term will be excluded from the Auto-Cancellation job. If any of the policy terms are Cancelled, the ERP must be created from the earliest cancellation transaction. Upon creating the ERP, the source term and all associated transactions, are locked. When deleting or voiding an ERP, the source term is automatically unlocked.

Once an ERP Endorsement is created, the Policy Information widget displays the policy Transaction and Status. The Valid Until Date field displays the date based on the ERP Duration Default value configured in the Master Cover. Users can choose to modify the ERP Duration date by clicking the date link in the widget and selecting a different option from the duration list dropdown in the modal. Users can also modify the Distributor on an ERP Endorsement when the transaction is in Incomplete or Quoted status from the modal. The existing functionality for changing the distributor on a policy applies to these transactions.

From the Client Information widget, users can modify the client in the Client Information modal. Any changes made here are saved to the client record in the system and the ERP Endorsement transaction.

Similar to other policy transactions, an ERP Endorsement can be quoted, bound, voided, marked as lost, and deleted and is displayed with the correct status as the submission transitions through the various steps.

Once an ERP is in Quoted status, it will display the Premium, Commission, Deductibles, Limits, and Taxes, however, the Premium for the ERP is not prorated. Users can configure multiple quote options for the ERP that will be available for selection when processing the transaction, however, Quote Versions are not supported. Note that the Request for Special Quote is also not supported for ERP Endorsements.

Users are able to mark and ERP Endorsement as Lost when a single Quote Option is configured.

If the billing module is enabled, the configured Payment Plan is carried forward from the prior policy term to the ERP Endorsement.

Once an ERP is Bound, the duration of the ERP cannot be modified. Users will have to void the ERP and start a new submission in order to change the ERP Duration.

Bound ERP Endorsements can also be imported via the Imports page in the Reference menu. The process and XML Import file follow the same structure as Renewal transactions.

ERP Endorsement functionality and configuration elements are only available to users with the appropriate security rights.

ERP Endorsement Transaction Validations and Restrictions

With the introduction of ERP Endorsements, the system now has additional validations and restrictions when processing these transactions and other related actions.

The following restrictions are notable:

  • Quote Versions are not supported for ERP Endorsements, and the action link is hidden from the Common Screens and Actions widgets when an ERP is created.
  • When voiding an ERP transaction, the Replace action link is not available as this is not supported for ERP Endorsements.
  • When the Product Type field is set to Claims-made, the Allow Program Policies setting in Policy Settings is hidden.

Generating Emails and Documents for ERP Endorsement Transactions

Similar to other policy transactions in the system, users can generate emails and documents that have been configured for the workflow.

Automatic Emails are generated when the user clicks on Calculate Quote, Bind, or Mark as Lost in the Actions widget and the ERP Endorsement is transitioned to either Quoted, Bound, or Marked as Lost status, respectively.

Documents can be generated automatically when the user clicks on Calculate Quote or Bind and the ERP Endorsement is transitioned to Quoted or Bound status.

  • For details on configuring emails for ERP Endorsements, see the Email Configurations section.
  • For details on configuring documents for ERP Endorsements, see the Documents / Forms section.

Single Installment Payment Plan for ERP Endorsement Transactions

A new transaction type field, ERP Endorsement, has been added to the Transaction Scheduling Rules panel in the Payment Plans section of the billing module. The field is set to Read-Only and has Single Payment as the selected option. Once the ERP Endorsement is Bound, the system generates and books the appropriate charges. Based on the General Ledger settings configured, the appropriate General Ledger entries are also created.

Note that charges associated to an ERP transaction are invoiced separately from other policy transactions and only a single installment is generated for ERP Endorsements.

Earnings Report for ERP Endorsement Transactions in Billing

An Earnings Report can be configured to generate the earnings related to ERP Endorsement transactions immediately upon binding the ERP Endorsement.

Once the ERP Endorsement is Bound and the transaction falls within the Reporting Period, the ERP is fully earned.

  • For details on configuring the Earnings Report, see the Earnings Report section.

Apply Sequencing to Field Evaluation Rules

The ability to specify sequencing for Field Evaluation Rules is now supported. This allows the user to better control the order in which individual rules are evaluated in relation to other Field Evaluation Rules configured within the submission workflow.

A new field called Sequence has been added to the General Information panel on the Field Evaluation Rule Management page. This is a mandatory field which is preloaded with the default value of zero for new configurations. For all existing rules configured before this feature, the default value has been set to 1 so that the system continues to evaluate them in the same order it did prior to this enhancement.

To apply sequencing, replace the default value with an integer value that represents the sequence order in which the Field Evaluation Rule should be evaluated. Continue with all other rules as needed.

Tip: It is advisable to leave gaps between the sequence numbers, such as 5, 10, 15. This allows new items to be added to the list at a later date, inserted between existing items. Otherwise, the sequence numbers of existing items must be changed to allow for the new addition.

Sequencing is now also supported for fields that are added to Field Evaluation Rules through the Fields panel. These fields are automatically sequenced by the system in increments of ten (10, 20, 30, etc) in the order in which they were selected in through the Bulk Add option in the Available Fields window. The sequence numbers for these fields can be edited as needed.

When viewing the Field Evaluation Rules list panel, the rules are listed in ascending order first by sequence number, then alphabetically. Note that Field Evaluation Rule sequence numbers are not displayed in the Workflow Dependency Tool.

Changes to Out Of Sequence Transactions and Billing

Previously, the system did not fully support integrations on the Calculate Quote action for OOS transactions, for integrations configured in the workflow container. The system has now been enhanced to allow integration configurations to work properly with Out of Sequence Endorsement and Adjustment transactions, and all associated replacement transactions.

In addition, the Out of Sequence Endorsement and Adjustment process will send the following information to the billing module:

  • All charges associated to the OOS transaction.
  • All charges associated to the Offset transaction as a result of the OOS transaction.
  • The Premium Earnings.

Manually Index Cross-Policy Data Configuration Fields

Cross-Policy Data Fields are automatically indexed at specific actions throughout the policy lifecycle. However, when introducing a new configuration, any transactions that were created prior to the introduction of the Cross-Policy Data Field are not indexed. Similarly, any correction made to one or more Associated Fields are not re-indexed for existing transactions. In order to trigger indexing for existing transactions, a data maintenance script was required.

The ability to schedule an indexing job for Cross-Policy Data Configurations is now supported. A new button called Schedule Indexing has been added to the Cross-Policy Data Configuration page for all new and existing configurations. Clicking this button opens the Schedule Indexing for Cross-Policy Data Fields window, which allows the user to assign the Start Date and Start Time for an indexing job for that particular configuration.

New Billing Fields Added to OWPolicyCommon Standard Container

Two new billing fields have been added to the OWPolicyCommon standard container. The Policy Outstanding Amount and Policy Remaining Unpaid Amount fields have been introduced to the Billing Information panel, in order to track the policy's total outstanding amounts to date and ensure that all Renewals are only Bound if the policy outstanding amounts associated to all previous terms are fully paid.

These fields are automatically updated by the system and must be added to a Cross-Policy Data Configuration in order to be updated correctly.

Claim Number Generation Configuration

Previously, a sequential claim number was assigned to each Notice of Intent submitted through the claims module. However, not all Notice of Intent submissions necessarily become valid claim submissions.

The ability to specify one or more claim Statuses or Status Sub-Statuses to determine whether the system generates and assigns a Claim Number is now supported. An Include/Exclude field containing all Statuses and Sub-Statuses configured within the claims module has been added to the Claim Number Generation panel on the General Settings - Sequence Numbering page to control this feature. Note that Notice of Intent is selected by default, but can be removed using the Include/Exclude control.

Viewing Generated Bill to Party Statements

Previously, statements that were generated for a bill to party were not accessible through the UI and could only be viewed when sending emails. A new Statements page is now available in the Bill to Parties section of the billing module in the Bridge Specialty Suite. Users with the appropriate ViewBilltoParty security right are now able to view a list of generated statements for the current bill to party. Clicking on the File Name link downloads a PDF copy of the statement to the user's local machine.

  • For details on viewing Bill to Party Statements, see the Statements section.

Invoice Distributor Commission Amounts for Canceled Policy Transactions

Previously, when a policy transaction was canceled, the only way to invoice the Distributor commission amount(s) was through an Offset transaction in the Outstanding Invoices page of the Bill to Party menu. While this functionality covers the majority of business cases, it can also occur that a policy transaction is canceled before any payable(s) have been logged within the billing module. In this scenario, the Distributor may or may not have yet been identified as a Bill to Party.

To allow users to collect the Distributor commission amount(s) for a Cancellation transaction before premium amounts have been collected, the Billing Adjustments feature has been enhanced. A new adjustment Category called Distributor Adjustment has been added to the General Information panel of the Billing Adjustments page. When selected, the Adjusted Party dropdown field is populated with a list of all Bill to Parties of type Distributor that have an active General Ledger Account.

Upon posting the Billing Adjustment the system determines whether the Distributor has been identified as a Bill to Party as part of an earlier policy transaction. If yes, the Distributor's billing cycle is updated with the adjustment amount. If not, the system automatically creates the Distributor as a Bill to Party and creates a new billing cycle for the adjustment amount. In either case, the current system date is identified as the billing start date for the adjustment amount.

New Optional Invoice Type Column Added to Invoices Report

A new optional Invoice Type(s) column can be added to the Invoices Report in the billing module. Users can add the new column by right-clicking in the column header section, clicking Select Columns, then clicking on the Invoice Type(s) option. Click Apply Changes to save the column selection.

The Invoice Type is identified based on the type of Charges associated to the invoice. If the invoice contains more than one charge type, a comma-separated list of the Charge Types is displayed.

New General Ledger Account Options & Logic

Upon posting a Batch Receipt in the billing module, the system automatically generates the corresponding General Ledger Report entries. To support separate Deductible Invoicing, the following three General Ledger Account types have now been added to the system.

  • Advanced Premium
  • Agency Bill Accounts Receivable
  • Deductible Accounts Receivable

Furthermore, the Accounts Receivable account has been relabeled to Premium Accounts Receivable to distinguish between different types of General Ledger accounts.

Each time a payment is applied against a premium invoice, an On Account Balance, or a deductible invoice, a General Ledger debit entry is entered for the Bank Account associated to the Batch Receipt. The account for the corresponding General Ledger credit entry is determined based on the invoice details.

  • If the Bill to Party type is either Direct (Client) or Insurer, the General Ledger credit entry is recorded in the Premium Accounts Receivable account.
  • If the payment is applied against an On Account Balance, the General Ledger credit entry is recorded in the Advanced Premium account.
  • If the Bill to Party type is Distributor, the General Ledger credit entry is recorded in the Agency Bill Account Receivables account.
  • For details on configuring a General Ledger Report, see the Managing General Ledger Accounts section.
  • For details on General Ledger Entries Report, see the General Ledger Entries Report section.

Managing General Ledger Account Codes

Policy field codes can now be used as placeholders to set G/L Codes for General Ledger Accounts when creating new G/L entries for Bound policies.

When creating a new General Ledger Account in the General Information panel, enter the placeholder [[GLCodefield1]] in the G/L Code field, where "GLCodefield1" is the field code of the policy custom field. If an invalid placeholder is entered, the code will remain as a string and will not return the appropriate value. Special characters are not supported for G/L Code values. Note that any special characters (including underscores, periods, and non-alphabetical characters), are not supported. If a special character is included in the policy custom field, the system displays a warning message.

Users can enter multiple field codes, individually enclosed in square brackets, within the placeholder. Each code must include the appropriate opening and closing brackets ( [[ ]] ), or the system will display a warning message.

General Ledger Account Reporting

The General Ledger documentation has been updated to reflect the available G/L accounts and entries based on the generation event.

As multiple new G/L accounts have been added to the billing module, the existing G/L accounts documentation now includes a description of each General Ledger Account and a sub-section describing the entries created.

New General Ledger Accounts for Invoice Entries

Two new General Ledger Account types have been added to the billing module in order to better track the billed amounts captured upon generating an invoice.

The Invoiced Taxes and Invoiced Commission Expense accounts are now available when managing General Ledger Accounts and the appropriate entries are added when generating an invoice. In addition, a Distributor lookup field has been added to the General Ledger Account modal when creating the Invoiced Commission Expense account type, in order to add the distributor associated to the invoice.

When an invoice is generated and the Book Policy Premium field is set to Policy Bind and the invoiced charges are of type Premium, the system creates the following entries in the Invoiced Taxes account:

  • Credit: A tax payable entry for the sum of the tax charges, per tax type, for the tax type associated to the invoice.
  • Debit: A debit entry for the sum of the tax charges associated to the invoice.

In addition to the above G/L entries, when an invoice is generated for the Bill to Party of type Distributor, the system creates the following entries in the Invoiced Commission Expense account:

  • Credit: A credit entry of Commission Payable - Distributor is added for the total commission charge amounts, per distributor.
  • Debit: A debit entry of Invoiced Commission Expense - Distributor is created for the sum of the total commission charges, per distributor, associated to the invoice.

New General Ledger Accounts for Write-Offs

Two new General Ledger Account types have been added to the billing module in order to track the Premium - Write Off entries separately from Deductible - Write Off entries.

The Write-Offs/Bad Debt G/L account has been renamed to Write Off - Premium and the following two accounts have been introduced:

  • Write Off - Deductible
  • Write Off - Other

Note that policy field placeholders can be entered in the G/L Code field and will display the appropriate field value when generated for Write Off - Premium accounts.

When Invoiced Charges are of type Premium, the system creates the following entries:

  • Debit: A debit entry for the Write Off - Premium account for the amount of the invoiced Premium charges upon write off.
  • Credit: A credit entry for the Premium Accounts Receivable account when the Bill to Party is of type Insured.
  • Credit: A credit entry for the Agency Bill Accounts Receivable account when the Bill to Party is of type Distributor.

When the Invoiced Charges are of type Deductible, the system creates the following entries:

  • Debit: A debit entry for the Write Off - Deductible account for the amount of the invoiced Deductible charges upon write off.
  • Credit: A credit entry for the Deductible Accounts Receivable account for the amount of the invoiced Deductible charges upon write off.

In the event that there are multiple types of invoiced charges being written off, the system will create the following entries:

  • Debit: A debit entry for the Write Off - Other account for the amount of the invoiced charges of any type upon write off.
  • Credit: A credit entry is created for the Agency Bill Accounts Receivable account if the Bill to Party is of type Distributor.
  • Credit: A credit entry is created for the Premium Accounts Receivable account if the Bill to Party is of type Assured.

New General Ledger Account Entries for Offset Transactions

Previously, the system did not generate General Ledger entries for Offset transactions. Following this release, when posting a Batch Receipt of type Offset, the system creates the following entries:

In the Clearing G/L account, a debit entry is created for the amount of the invoiced policy term when an Offset transaction is created.

When the invoiced charges are of type Premium, the system creates the following entries:

In the Agency Bill Accounts Receivable account:

  • Credit: A credit entry is created for the amount of the invoiced charges of type Premium when an Offset transaction is created, if the Bill to Party associated to the invoice is of type Distributor.

In the Premium Accounts Receivable account:

  • Credit: A credit entry is created for the amount of the invoiced charges of type Premium when an Offset transaction is created, if the Bill to Party associated to the invoice is of type Insured.

When the invoiced charges are of type Deductible, the system creates the following:

In the Deductible Accounts Receivable account:

  • Credit: A credit entry is created for the amount of the invoiced charges of type Deductible upon creating an Offset transaction.

When the invoiced charges are of type Claim Payment, the system creates the following:

In the Paid Claims Receivable account:

  • Credit: A credit entry is created for the amount of invoiced charges of type Claim Payment upon creating an Offset transaction.

Note that when reversing a Batch Receipt of type Offset, debit entries are created in the Clearing account, while credit entries are created for the Agency Bill Accounts Receivable, Premium Accounts Receivable, Deductible Accounts Receivable, and Paid Claims Receivable G/L accounts.

New General Ledger Account Entries for Adjustments and Deductible Recovery

Previously, the system did not generate General Ledger entries for Billing Adjustments and Deductible Recovery. Following this release, when generating a Deductible invoice, the system creates the following entries:

For Deductible Recovery entries, a new G/L account type of Clearing - Claims Payable has been added. When generating an invoice of type Deductible, where the total invoice outstanding amount is negative, the system will create the following:

  • Credit: A credit entry in the Clearing - Claims Payable account.
  • Debit: A debit entry in the Deductible Recovery - Indemnity account when Deductible - Indemnity charges are selected on the invoice.
  • Debit: A debit entry in the Deductible Recovery - Expense account when Deductible - Expense charges are selected on the invoice.

When generating an invoice of type Deductible, where the total invoice outstanding amount is positive, the system will create the following:

  • Debit: A debit entry in the Deductible Accounts Receivables account.
  • Credit: A credit entry in the Deductible Recovery - Indemnity account when Deductible - Indemnity charges are selected on the invoice.
  • Credit: A credit entry in the Deductible Recovery - Expense account when Deductible - Expense charges are selected on the invoice.

When generating an invoice with charges of type Billing Adjustment and when the Adjustment Category is Distributor the system generates the following entry for the Agency Bill Accounts Receivables account:

  • Debit: A debit entry is created for the amount of the invoiced charges of type Billing Adjustment when the Adjustment Category is Distributor.
  • Credit: A credit entry is created for the amount of the invoiced charges of type Billing Adjustment and the Adjustment Category is Distributor.

Upon posting a cash receipt for an invoice with charges of type Billing Adjustment and when the Adjustment Category is Distributor the system generates the following entry for the Agency Bill Accounts Receivables account:

  • Credit: A credit entry is created for the total amount of the invoiced charges of type Billing Adjustment when posting a cash receipt, if the Adjustment Category is Distributor.
  • Debit: A debit entry is created for the total amount of the invoiced charges of type Billing Adjustment when posting a cash receipt, if the Adjustment Category is Distributor.
  • For details on the Billing Adjustment and Deductible Recovery G/L entries, see the General Ledger Accounts section.

New General Ledger Account Entries for Reinstatement Transactions

The system is now generating General Ledger entries for Reinstatement transactions. Following this release, when a Reinstatement is Bound and the Book Policy Premium On setting is set to Bind for the policy's Billing Entity, the system creates the following entries.

Debit entries are created for the following accounts:

  • The Agency Bill Account Receivables account for the amount of the Cancellation receivables less the sum of the Clearing amount and On Account amounts associated to the policy term, when the Billing Option is set to Agency.
  • The Premium Account Receivables account for the amount of the Cancellation receivables less the sum of the Clearing amount and On Account amounts associated to the policy term, when the Billing Option is set to Direct.
  • The Commission Expense G/L account for the sum of commission charges, per Premium Type, associated to the policy Reinstatement transaction.
  • The Clearing G/L account for the Cancellation Clearing amounts less the On Account amount associated to the policy term.

Credit entries are created in the following accounts:

  • The Written Premium G/L account for the sum of charges gross amount, per Premium Type, for the associated policy Reinstatement premium type.
  • The Tax Payable G/L account for the sum of charges gross amount, per Tax Type, for the associated policy Reinstatement tax type.
  • The Accounts Payable Distributor G/L account for the sum of commission charges, per Distributor, for the associated policy Reinstatement distributor, when the policy term's Billing Option is set to Direct.

    If the Billing Option is set to Agency, this entry is not created.

Note that if the Book Premium On setting is set to Invoice Generation, these entries are not created.

Booking Premium Accounts Receivable Amounts

Previously, all charges including charges of type Premium were logged in the appropriate General Ledger account upon the Invoice Generation event. There was no alternative option available.

To help licensees better control the booking of written Premium, the system now supports the alternate option of logging charges of type Premium in the appropriate General Ledger accounts once the source transaction transitions into Bound status.

As a result of this feature, the Managing General Ledgers menu item in the Billing Entity Menu has been relabeled General Ledger, with two sub-menu options: Settings and Accounts. The Settings page contains the option to change the newly introduced Book Policy Premium on field from Invoice Generation (the default value) to Policy Bind. The Accounts page contains the previously supported General Ledger Account List panel, where the user can manage General Ledger accounts.

Note that this option is only supported for charges of type Premium. All other General Ledger entries continue to be generated upon the Invoice Generation event.

Marking Distributor Debit Payables as Paid

Previously, users were unable to mark Distributor debit payables as Paid. However, there are business scenarios where cancellation transactions are created and the agent must return the Commission amount back to the insurer.

Now, users can mark Debit Payables as Paid via the Distributor Payables page. When a cancellation transaction is invoiced and the Refund Batch is marked as Ready for Payment, it will appear in the Distributor Payable Journal. Select the invoice with the cancelled policy and click Mark as Paid. The Payment modal is displayed where the user can enter the financial details of the bank account. Once submitted, the invoice transitions to Paid status.

Once the debit payable is in Paid status, the appropriate G/L entries are made in the Bank Account - Account Name Debit and Accounts Payable - Distributor reports, if configured.

The previous validation message that prevented users from marking these payables as paid has been removed.

Marking On Account Balance Amounts as Eligible for Refund or Reserve for Future Installments

Users working within the billing module can now select whether On Account Balance amounts should be reserved for Future Installments or are eligible for Refunds.

A new dropdown, Reserve On Account Amount to Future Installments, has been added to the On Account Balance grid in the On Account Balance Details modal and lists the options available for the On Account Balance amount. Users can select Yes - All Invoices, Yes - Deductible Invoices, Yes - Non Deductible Invoices (any invoices other than deductible, i.e. premium), or No.

Additionally, two new fields, Reserve On Account Amount To Future Installments and Automatically Apply to Invoices of Type, are displayed on the Receipt Information panel for posted batch receipts. These fields display the value of the selection made in the Reserve On Account Amount to Future Installments column on the On Account Balance grid. By default, the Automatically Apply to Invoices of Type field is set to Non - Deductible.

  • For details on viewing On Account Balance amounts for Bill to Parties, see the On Account Balance section.

Invoice Type and Assured Names Columns Listed on Outstanding Invoices Grid

Two new columns, Invoice Type and Assured Names, have been added to the Outstanding Invoices grid on the Receipt Allocation Invoice modal of the Receipt Details Allocation page. The Invoice Type column displays the Charge type, however, does not display the Account Balance Allocation. The Assured Names column displays the names of the Assureds associated to the receipt. Multiple Assureds will be comma-separated.

The Invoice Type is automatically set based on the invoice payment association as follows:

  • If the Invoice is associated to Premium charges only, the Invoice Type is Premium Activity.
  • If the Invoice is associated to Deductible charges only, the Invoice Type is Deductible.
  • If the Invoice is associated to Claim Payment charges only, the Invoice Type is Claim Payment.
  • If the Invoice is associated to Billing Adjustment charges only, the Invoice Type is Billing Adjustment.

Note that if the invoice is associated to more than one Charge Type, the Invoice Type is left empty.

Upon clicking Add in the Invoice Allocations panel, the Invoices modal is displayed. By default these additional columns are hidden, and can be displayed on the Outstanding Invoices grid by right-clicking on the column headers to display the contextual menu. Click Select Columns to display the additional columns to be added and select Invoice Type and Assured Names, then click Apply Changes to reload the grid with the newly added columns.

Claims Workflow Configuration for Cross-Product Integration

In order to successfully integrate with Insurity's ClaimsXpress application, users must configure additional fields in a Claims workflow to correctly transfer data from one application to the other. A list of fields and field codes must be configured in the workflow container, however, they do not have to be added to any specific panel or screen, as per the usual configuration.

In addition to the specified fields, certain of these fields are required to be set to Calculated and contain the appropriate placeholder/formula.

If you require this functionality, please contact your Insurity Account Representative.